Remove securityGroupOverride validation for NLB #17383
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #17207
NLBs did not support security groups in the past. However, AWS now supports specifying a security group for an NLB. When kops creates a new cluster with an NLB, it also creates a security group for it by default.
Therefore, I believe we can now allow
securityGroupOverride
for NLBs in kops as well.Please let me know if I'm overlooking anything or if there are any concerns with this approach.